API

System APIs

PUT system/rambase-event-types/{rambaseEventTypeId}/parameters/{parameterId}

Updates provided RamBase event type parameter

HTTP method PUT
URI https://api.rambase.net/system/rambase-event-types/{rambaseEventTypeId}/parameters/{parameterId}
Supported formats Xml, Html, Json (ex. $format=json)
- URI parameter {rambaseEventTypeId} RamBase event type identifier
Integer, minimum 100000
- URI parameter {parameterId} RamBase event type parameter identifier
Integer, minimum 1
Successful HTTP status code 200
API resource identifier 270, version 9

The following body must be added to the request. Mouse over fieldnames for description and other useful information about the fields. Note that fields in bold are required/mandatory.

Format:
1
<RamBaseEventTypeParameter
RamBaseEventTypeParameter

This field is optional.

>
2
     <Key
Key

Name of the parameter

This field is optional.

>
{String}</Key>
3
     <Datatype
Datatype

The datatype of the parameter

Applicable domain values can be found here

This field is optional.

>
{String}</Datatype>
4
     <IsRequired
IsRequired

Determines whether or not this parameter is required for all Events of this Event Type (Y / N)

This field is optional.

>
{Boolean}</IsRequired>
5
</RamBaseEventTypeParameter>
1
{
2
     "ramBaseEventTypeParameter
RamBaseEventTypeParameter

This field is optional.

":
{
3
          "key
Key

Name of the parameter

This field is optional.

":
"{String}",
4
          "datatype
Datatype

The datatype of the parameter

Applicable domain values can be found here

This field is optional.

":
"{String}",
5
          "isRequired
IsRequired

Determines whether or not this parameter is required for all Events of this Event Type (Y / N)

This field is optional.

":
"{Boolean}"
6
     }
7
}

The query string is placed after the resource URL, seperated with a questionmark (?). The query string is composed of a series of query parameters with values. See the page about query parameters on how to use these parameters.

$access_token String, optional After successful login you get an access token which needs to be provided in all API requests. Even though it is possible to pass this token as query parameter, we recommended passing it using the HTTP request header as described in Authorization. Note that all access tokens have an expiration time.
$db String, optional Set the database/company for the request
$useMinimumVersion Integer, optional Used to run a new version of an API resource when your API client is running a deprecated API resource. See the Breaking changes page for more information.

Read more about filters and sorting on how to use filter parameters and named filters.

Read more about filters and sorting on how to use sortable parameters

Requesting this resource will yield the following response. Mouse over fieldnames (or fieldgroups) for descriptions and other useful information about the fields. Fields colored in grey is expandable fields.

Please note that some fields may be removed from the response, based on user roles/duties/permissions.

Format:
1
1

List of available operations/actions for this resource.
See the operations documentation for more information about API operations.

Possible error codes the response might return:

Error 102529 HTTP 404 RamBase event type not found
Error 102568 HTTP 400 Parameter keys must be unique
Error 101640 HTTP 400 Data type is required